Options


+OPTIONS statement


Optionally you can define an +OPTIONS Statement, which is here mainly for debugging purposes:

+OPTIONS STOPAFT=xxxxx,SKIPREC=xxxxx,DUMPREC=,LRECL=,HITS=



  • SKIPREC= This specifies the number of record that will be bypassed before any conditional checking will take place. SKIPREC will be tested before the STOPAFT keyword. Max. value allowed is ‚999999999‘. Default: 0 - no records will be skipped.


  • STOPAFT(ER)= The filtering program will no longer perform any conditional checking as defined in the //FLTINPUT. That means bypassing any tests after x-amount records. The records appear as ‚bypassed‘ in the statistics. Max. value allowed is ‚999999999‘. Default: 0 - all records will be processed.


  • DUMPREC= This function allows to dump in hex format the records before any conditional check takes place. You can specify DUMPREC=V or DUMPREC=F. If DUMPREC=V is specified, the number of bytes to be dumped will be extracted from the RDW i.e. from the first 2 bytes of a record retrieved. The records will be dumped before any conditional checking takes place - refer to HITS= as well. (DUMPREC is similar to known HEXDUMP or HEXPRINT functions). Default: none


  • LRECL= Specifies how many bytes should be dumped. This information is required in case data is passed in the fixed format for records that have e.g. DCB attributes LRECL=80 etc. Max. value allowed is ‚32760‘. Do not specify the keyword LRECL= for files which have the DCB=RECFM=V(ariable) format. The length will be automatically extracted from the RDW(record description word - byte 0 and 1) in such a case. It is the users responsibility to define the correct values. Default: 0.


  • HITS=ONLY. If this keyword is specified together with the DUMPREC keyword, it will cause that only records which match the COND= statement are dumped. Default: all records will be dumped in case DUMPREC was specified.


+OPTIONS statement sample
//FLTPRINT DD SYSOUT=*
//FLTINPUT DD *
+OPTIONS DUMPREC=V,HITS=ONLY
+INCLUDE . . . . . .

//


The function described above may be very valuable in case you want to view the content of SMF records.